Search results

Developing software for processing bibliographic materials in the Arabic language is a relatively recent development. When libraries in parts of the Middle East, where Arabic is the main language, started automating their collections, most library systems did not provide for the use of Arabic script and this capability had to be developed. Automated library systems started to emerge (like Minisis, ALEPH, Dobis/Libis, TinLib, OLIB) to fill the gap for non‐Roman scripts. This article describes the stages the American University of Beirut Libraries went through in converting their Arabic materials for use in the OLIB7 library management system. A description of the background of the library is given along with the details of the romanisation process, the conversion process, the software and hardware chosen, the testing of the database, problems encountered, output and the handling of authority records.

Database quality problems have been a major concern in recent years. With the increasing number of databases mounted online and on CD‐ROM, users are more exposed to errors affecting the quality of their search. This article draws attention to database quality problems in Library and Information Services (LIS) through a review of the literature concentrating on the implication of poor quality on users, work undertaken in the area and measures taken for further quality improvement. The Centre for Information Quality Management (CIQM) has been set up in the UK to deal with database quality problems. A CIQM project funded by the British Library, is investigating database quality problems and their effects on users. Suggestions for reducing database quality problems have been given by a variety of authors whose common idea is the creation of an organisation similar to CIQM, and an international standard which producers could use to provide higher quality databases.

To describe the restructuring project of the portal BioLib at the Institut Pasteur Library in Paris and to share experiences with others facing similar challenges.

Provides an outline of the history and the steps followed during the initial project (2001), an evaluation of the use of the portal and the stages in restructuring the portal for its subsequent relaunch in 2006.

The initial portal was not used because of lack of a friendly interface and poor content. Information is provided about the concept and functionalities of a portal, what can go wrong, and how to make it survive.

A useful source of information for professionals wishing to develop a portal or conduct a similar project with the “dos” and “taboos” to take into account.